Skip to content

feature(cluster): use DynamicWhiteListRoundRobinPolicy for public address connections#14512

Draft
fruch wants to merge 1 commit intoscylladb:masterfrom
fruch:use-dynamic-whitelist-policy
Draft

feature(cluster): use DynamicWhiteListRoundRobinPolicy for public address connections#14512
fruch wants to merge 1 commit intoscylladb:masterfrom
fruch:use-dynamic-whitelist-policy

Conversation

@fruch
Copy link
Copy Markdown
Contributor

@fruch fruch commented May 4, 2026

Summary

  • Switch python-driver to use scylladb/python-driver#833 (branch dk/fix-for-proxy-access-2-with-license-fix) which introduces DynamicWhiteListRoundRobinPolicy
  • When SCT connects via public addresses (IP_SSH_CONNECTIONS == "public"), use DynamicWhiteListRoundRobinPolicy instead of WhiteListRoundRobinPolicy
  • Add helper script run-ami-artifact-test.sh for running AMI artifact tests with public communication

Motivation

When connecting to Scylla nodes via public IPs, the driver discovers private IPs from system tables that are unreachable from the client. DynamicWhiteListRoundRobinPolicy solves this by dynamically tracking which host the control connection resolves to and only routing queries there.

Dependencies

…ress connections

Switch python-driver to PR scylladb/python-driver#833 branch which
introduces DynamicWhiteListRoundRobinPolicy. When SCT connects via
public addresses (IP_SSH_CONNECTIONS == "public"), use this policy
instead of WhiteListRoundRobinPolicy.

DynamicWhiteListRoundRobinPolicy dynamically tracks which host the
control connection resolves to and only routes queries there, solving
the problem where the driver discovers private IPs from system tables
that are unreachable from the client when using public/proxy access.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant